Repository navigation
moe: expert slots in size classes (Flash-Next: 34.4 -> 27.0 GiB pinned for the same slots) - #137
Conversation
….0 GiB pinned) Mixed-quant (UD) models use bigger types for some layers' experts. One slot size, the largest, wasted up to 22% of the pinned memory. Layers are now grouped by the bytes one expert needs; each group has its own slots and LRU, and every layer keeps the same share of its experts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Docs7 for 1bit-monster/engine
Commit |
PR Reviewer Guide 🔍(Review updated until commit ba4c23f)Here are some key observations to aid the review process:
|
|
Persistent review updated to latest commit ba4c23f |
Unsloth's UD quants use bigger types for some layers' experts. With one slot size, the largest, Flash-Next's 9,216 slots pinned 34.4 GiB for 27.5 GiB of expert data. Qwen3-Coder-30B Q4_K_M, which uses Q6_K for some layers' down projection, pinned 8.8 GiB.
ExpertCachenow groups layers by the bytes one expert needs (the sum of its aligned read windows). Each group has its own slots and LRU, or one LRU per layer with--per-layer, and every layer keeps the same share of its experts.Measured on Strix Halo with
1bit moe-cache:A Coder-30B chat replay runs normally: 95.2% hits, 33.9 tok/s at 12.1 ms compute.
The trade-off: the shared LRU no longer moves budget between size classes. Flash-Next has 2 classes, and most models have one.
🤖 Generated with Claude Code